-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #15008: Add a "Rudder by example" to add CPU vulnerabilities status to inventory #584
Conversation
f4d5912
to
c4dc27d
Compare
Commit modified |
c4dc27d
to
4c898ca
Compare
Commit modified |
4c898ca
to
1ce3a72
Compare
Commit modified |
|
||
An inventory extension script can be written in any language, it just needs to be an | ||
executable file placed in `/var/rudder/hooks.d` that outputs a json object. It will be called at each | ||
inventory,and its output will be added into it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing space after comma
* Determine the status of the node for each known vulnerability | ||
* Add details in a separate variable for mode advanced handling | ||
|
||
In our case, we have write a small python script (the https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.py[script] and its https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.adoc[documentation]) that outputs our CPU vulnerabilities in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we wrote or we have written
Commit modified |
This PR is not mergeable to upper versions. |
OK, squash merging this PR |
…status to inventory
ed22d1c
to
bf4536d
Compare
https://issues.rudder.io/issues/15008